Balancing Clients Across Bands in a Single Access Point

ABSTRACT

Balancing client load on an access point in a wireless digital network. An access point tracks the number of connected users and accepts new connections only if the number of connected users is below a preset threshold. The number of connected users may be tracked on an access point wide basis, a per-band basis, a per-BSSID basis, or a combination. Similarly, accepting new connections may be done on an access point wide basis, a per-band basis, a per-BSSID basis, on the basis of client 802.11 capabilities, or a combination.

BACKGROUND OF THE INVENTION

The present invention relates to wireless digital networks, and in particular, to the problem of balancing client load across bands in an access point in a wireless digital network.

Wireless digital networks commonly have a controller to which are attached one or more access points. Each access point supports a number of wireless clients. In most situations, each access point (AP) connects to its controller using a wired connection, for example using 803.2 Ethernet.

An access point may advertise multiple services (SSIDs) on different bands. As an example, IEEE802.11 wireless networks in the United States may operate on channels on the 2.4 GHz and 5 GHz bands, advertising services to wireless clients on each band.

The resources in a access point in a single band are limited. If an access point accepts too many client connections, it may not have the resources needed to adequately service all those clients. Typically, client devices do not have a sense of the load on an individual access point, or the load on a particular band on an access point. Client devices commonly choose an access point to associate with based on reported signal strength, often choosing the access point with the strongest signal.

What is needed is a mechanism for balancing client load across different bands in a single access point. dr

BRIEF DESCRIPTION OF THE DRAWINGS

The invention may be best understood by referring to the following description and accompanying drawings that are used to illustrate embodiments of the invention in which:

FIG. 1 shows an access point in a wireless network.

DETAILED DESCRIPTION

Embodiments of the invention relate to methods of balancing client load in a single access point (AP) in a wireless network. In an embodiment of the invention an AP in a wireless network advertises services on one or more bands. The access point keeps track of the number of wireless clients connected to it. As wireless clients attempt to connect to the access point, the access point checks the number of connected clients and only allows new connections is the number of wireless clients currently connected to the access point is below a threshold. The access point will not respond to Probe Requests from unconnected clients, and will respond to Authentication Requests from new clients with an error response if the access point is overloaded. The determination of connected clients being below a threshold to allow new connections may be made on an overall access point basis, on a per-band basis, a per-BSSID basis, or a combination. The determination can also be made based on client capabilities advertized by the client in a Probe Request frame allowing 802.11n clients on the 5 GHz band and keeping legacy non 802.11n capable clients in 2.4 GHz band.

FIG. 1 shows a network in which access point 100 supports wireless clients 200 a, 200 b.

Access point 100 is a purpose-built digital devices having a CPU 110, memory hierarchy 120, a first wired interface 130, and wireless interface 140. The CPU 110 commonly used for such access nodes is a MIPS-class CPU such as one from Raza Microelectronics or Cavium Networks, although processors from other vendors such as Intel, AMD, Freescale, and IBM may be used. Memory hierarchy 120 comprises read-only storage such as ROM or EEPROM for device startup and initialization, fast read-write storage such as DRAM for holding operating programs and data, and permanent bulk file storage such as compact flash memory. Memory hierarchy 120 may also contain a TPM. Access point 100 typically operates under control of purpose-built programs running on an embedded operating system such as Linux or VXWorks. Wireless interface 140 is typically an interface operating to the family of IEEE 802.11 standards including but not limited to 802.11a, b, g, and/or n. A typical access point may have multiple wireless interfaces 140, for example, one wireless interface providing services on the 2.4 GHz band, and one wireless interface 140 providing services on the 5 GHz band.

In operation access point 100 advertises services on each band in which it operates by advertising services through one or more broadcast BSSIDs. Access point 100 responds to Probe Requests from client devices 200, Authentication Requests and Association Request from client devices 200 enable client devices 200 to connect to the access point.

Client devices typically select an access point from a set of available access points based on signal strength. This can lead to the overloading of one access point in an area, as clients connect to the highest signal strength provider. Signal Strength is generally stronger in 2.4 GHz band and clients tend to favor connecting on that band.

According to the present invention, access point 100 keeps track of the number of users connected to it. If access point 100 is overloaded, based on the number of users connected to it, the access point will not accept new connection requests.

Not accepting connection requests means for example that access point 100 will only respond to Probe Requests if it is not overloaded. Conversely, the access point will not respond to Probe Requests when overloaded. In normal, non-overloaded operation, access point 100 responds to Authentication Requests with an Authentication Response. When overloaded, access point 100 responds to Authentication Requests with an Authentication Response containing an error code, rejecting the request. In normal, non-overloaded operation, access point 100 responds to Association Request with an Association Response containing a success code. When overloaded, access point 100 responses to an Association Response with an error code, rejecting the request.

In one embodiment of the invention, access point 100 makes the decision of being overloaded or not being overloaded based on the number of users connected on each band. As an example, for a dual-band access point providing services on both 2.4 GHz and 5 GHz bands, the access point may have a limit of 20 connected clients using a 20 MHz wide channel on the 2.4 GHz band, and 45 connected clients using a 40 MHz wide channel on the 5 GHz band. Once the access point has its maximum number of connections on the 5 GHz band, it will stop accepting connection requests on the 5 GHz band, but may still respond to connection requests on the 2.4 GHz band if that band is not overloaded. If the access point has its maximum number of connections on the 2.4 GHz band, it will stop accepting connection requests on that band, but may accept connection requests on the 5 GHz band if the access point is not overloaded on that band.

In another embodiment of the invention, these rules may be combined.

In another embodiment of the invention, access point 100 may make the decision of being overloaded or not overloaded on a per-band and per-BSSID basis. As an example, an access point may support voice-over-IP (VOIP) services on the 2.4 GHz band through a particular BSSID. According to the present invention, the access point may only allow a certain number of client connections to that BSSID before it will stop accepting connection requests. The access point may stop accepting connection requests just to that BSSID, on that band, or to the access point entirely.

As an example, in an embodiment of the invention, if an access point has accepted clients on one BSSID, such as a 2.4 GHz VOIP BSSID, the access point may only accept new connection requests on the 5 GHz band until a further threshold is reached.

In another embodiment of the invention, access point 100 may make the decision of being overloaded or not on parameters such as client 802.11 capabilities. As an example, an access point may only accept new high throughput connections, such as IEEE802.11n connections until a maximum number of such connections is reached. Such capabilities are generally advertized in Probe Request sent by the client to the Access Point.

The present invention may be realized in hardware, software, or a combination of hardware and software. The present invention may be realized in a centralized fashion in one computer system, or in a distributed fashion where different elements are spread across several interconnected computer systems. Any kind of computer system or other apparatus adapted for carrying out the methods described herein is suited. A typical combination of hardware and software may be a general purpose computer system with a computer program that, when being loaded and executed, controls the computer system such that it carries out the methods described herein.

The present invention also may be embedded in a computer program product, which comprises all the features enabling the implementation of the methods described herein, and which when loaded in a computer system is able to carry out these methods. Computer program in the present context means any expression, in any language, code or notation, of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or after either or both of the following: a) conversion to another language, code or notation; b) reproduction in a different material form.

This invention may be embodied in other forms without departing from the spirit or essential attributes thereof. Accordingly, reference should be made to the following claims, rather than to the foregoing specification, as indicating the scope of the invention. 

1. A method of operating an access point in a wireless network comprising: tracking in the access point the number of wireless clients connected to the access point, and allowing new connections to the access point if the number of wireless clients connected to the access point is below a predetermined threshold.
 2. The method of claim 1 where the tracking in the access point the number of wireless clients connected to the access point is performed on an access-point wide basis.
 3. The method of claim 1 where the tracking in the access point the number of wireless clients connected to the access point is performed on a per-band basis.
 4. The method of claim 1 where the tracking in the access point the number of wireless clients connected to the access point is performed on a per-BSSID basis.
 5. The method of claim 1 where allowing new connections to the access point if the number of wireless clients connected to the access point is below a predetermined threshold is performed on an access-point wide basis.
 6. The method of claim 1 where allowing new connections to the access point if the number of wireless clients connected to the access point is below a predetermined threshold is performed on a per-band basis.
 7. The method of claim 1 where allowing new connections to the access point if the number of wireless clients connected to the access point is below a predetermined threshold is performed on a per-BSSID basis.
 8. The method of claim 1 where allowing new connections to the access point if the number of wireless clients connected to the access point is below a predetermined threshold is performed on the basis of client 802.11 capabilities.
 9. Software for operating an access point in a wireless network comprising: a tracker for tracking the number of connections made to the access point, and an accepter controlling new connections, wherein new connections are only accepted if the tracker indicates the number of connections made to the access point is below a threshold, wherein the tracker and the accepter are software digitally encoded in a computer readable medium executable by a computing device, which causes the computing device to perform a set of actions for which the tracker and the accepter are configured.
 10. The software of claim 9 where the tracker tracks the number of connections made to the access point on an access point wide basis.
 11. The software of claim 9 where the tracker tracks the number of connections made to the access point on a per-band basis.
 12. The software of claim 9 where the tracker tracks the number of connections made to the access point on a per-BSSID basis.
 13. The software of claim 9 where the accepter accepts new connections on an access point wide basis.
 14. The software of claim 9 where the accepter accepts new connections on a per-band basis.
 15. The software of claim 9 where the accepter accepts new connections on a per-BSSID basis.
 16. The software of claim 9 where the accepter accepts new connections based on client 802.11 capabilities. 